Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dca988284e29cef87e755fcd7547b5172981ba18d23fda7244d4bf2220e0f11

Tx prefix hash: e03c28de1921bee24aca1fd8eb3c2e7af3ae2cae268852c46f23e2652d3e6950
Tx public key: 10cd85834280fe11fc715ba87513ddf75c8ea6099ff26c12ff07ad1e5d4ac02c
Timestamp: 1661218088 Timestamp [UCT]: 2022-08-23 01:28:08 Age [y:d:h:m:s]: 03:070:12:27:22
Block: 571756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830216 RingCT/type: yes/0
Extra: 0110cd85834280fe11fc715ba87513ddf75c8ea6099ff26c12ff07ad1e5d4ac02c021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.825914975000 dcy

stealth address amount amount idx
00: 44dbec1cba373ed827c2dc064cb5124c3c5dc85ccd4093245cf09819209e0b7a 7.825914975000 1004980 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": 571766, "vin": [ { "gen": { "height": 571756 } } ], "vout": [ { "amount": 7825914975, "target": { "key": "44dbec1cba373ed827c2dc064cb5124c3c5dc85ccd4093245cf09819209e0b7a" } } ], "extra": [ 1, 16, 205, 133, 131, 66, 128, 254, 17, 252, 113, 91, 168, 117, 19, 221, 247, 92, 142, 166, 9, 159, 242, 108, 18, 255, 7, 173, 30, 93, 74, 192, 44, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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