Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1236d63f2f30bfd845da4dc397b9e92be415a22b332ab6d4cc181e178ba12755

Tx prefix hash: 7cbfae6269bddad2f7d4f1e9cd9340a55569afd0f645ce0ad664df702fa19154
Tx public key: 926fda40ec2147c0e0f90e0f5115596cb1e08554a19e00b8123f55d8b5790407
Timestamp: 1714078792 Timestamp [UCT]: 2024-04-25 20:59:52 Age [y:d:h:m:s]: 00:305:08:50:30
Block: 1008456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218274 RingCT/type: yes/0
Extra: 01926fda40ec2147c0e0f90e0f5115596cb1e08554a19e00b8123f55d8b57904070211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84ca4caa438552f3e2c226656a345dc12ea52a7eeb134476d1f0d14574d2e5da 0.600000000000 1469926 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": 1008466, "vin": [ { "gen": { "height": 1008456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84ca4caa438552f3e2c226656a345dc12ea52a7eeb134476d1f0d14574d2e5da" } } ], "extra": [ 1, 146, 111, 218, 64, 236, 33, 71, 192, 224, 249, 14, 15, 81, 21, 89, 108, 177, 224, 133, 84, 161, 158, 0, 184, 18, 63, 85, 216, 181, 121, 4, 7, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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