Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cefdf133c7bfa086c492e02b1ad14b6f08420e055c4b4b4ee9379f1f5fabc37

Tx prefix hash: 93f16c59cf775840614fa0e56619917f1df3cd90f6f142d87b12c8d0671378be
Tx public key: dc667afcab0f980de9ecdea9a33989c2c615dc53c2c548f5a915e420717d2355
Timestamp: 1705400834 Timestamp [UCT]: 2024-01-16 10:27:14 Age [y:d:h:m:s]: 01:298:07:06:46
Block: 936500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472021 RingCT/type: yes/0
Extra: 01dc667afcab0f980de9ecdea9a33989c2c615dc53c2c548f5a915e420717d235502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da6e4e9753fce108e8c56ed0abf3352156c0f94405e95f774b9a745a63b69ec0 0.600000000000 1394528 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": 936510, "vin": [ { "gen": { "height": 936500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da6e4e9753fce108e8c56ed0abf3352156c0f94405e95f774b9a745a63b69ec0" } } ], "extra": [ 1, 220, 102, 122, 252, 171, 15, 152, 13, 233, 236, 222, 169, 163, 57, 137, 194, 198, 21, 220, 83, 194, 197, 72, 245, 169, 21, 228, 32, 113, 125, 35, 85, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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