Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7530a04e896e655a331866a379c8362ad926ef84907cb598dc87c570b2d8c3

Tx prefix hash: cef24b41f8a17cf474dff9fc9ef7ce2e90281c588aae01cd03b8e3c71aa569d8
Tx public key: 3e4adbbdfd280c23f59cb19d38fc92b37277aa2ffd0f28b77ff29369545e0402
Timestamp: 1721796346 Timestamp [UCT]: 2024-07-24 04:45:46 Age [y:d:h:m:s]: 00:091:23:48:10
Block: 1072442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65871 RingCT/type: yes/0
Extra: 013e4adbbdfd280c23f59cb19d38fc92b37277aa2ffd0f28b77ff29369545e0402021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf6463a13fe049a687c2ab095278e2c65b56c52172203748bcf02816a684a01 0.600000000000 1544911 of 15

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": 1072452, "vin": [ { "gen": { "height": 1072442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf6463a13fe049a687c2ab095278e2c65b56c52172203748bcf02816a684a01" } } ], "extra": [ 1, 62, 74, 219, 189, 253, 40, 12, 35, 245, 156, 177, 157, 56, 252, 146, 179, 114, 119, 170, 47, 253, 15, 40, 183, 127, 242, 147, 105, 84, 94, 4, 2, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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