Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0b1b06a2eff17a36c12616e17a75f3816fb682bebfc2c2b98d889c9cf0bd787b

Tx prefix hash: 568d41e8d47951cb137a84908fe1aa279145d3acfdfb9e2d54a5b5162ff3fdd4
Tx public key: 8f6394f6c61be2c7e4ce5d0a891f8c4aef6e72e2988b123fab26873a13950882
Timestamp: 1631775614 Timestamp [UCT]: 2021-09-16 07:00:14 Age [y:d:h:m:s]: 03:146:00:04:16
Block: 334782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879840 RingCT/type: yes/0
Extra: 018f6394f6c61be2c7e4ce5d0a891f8c4aef6e72e2988b123fab26873a13950882021100000008fdc024ec000000000000000000

1 output(s) for total of 47.723105722000 dcy

stealth address amount amount idx
00: b7cab6d5686084165df0a9fd048ec9a150aebe70ae46f1d6fba6be349ab5dd02 47.723105722000 690355 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 334792, "vin": [ { "gen": { "height": 334782 } } ], "vout": [ { "amount": 47723105722, "target": { "key": "b7cab6d5686084165df0a9fd048ec9a150aebe70ae46f1d6fba6be349ab5dd02" } } ], "extra": [ 1, 143, 99, 148, 246, 198, 27, 226, 199, 228, 206, 93, 10, 137, 31, 140, 74, 239, 110, 114, 226, 152, 139, 18, 63, 171, 38, 135, 58, 19, 149, 8, 130, 2, 17, 0, 0, 0, 8, 253, 192, 36, 236, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8