Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a771bacea868883e2cb129251dbcd650425237604572770dad6859895ccaa0da

Tx prefix hash: a561865b22a0282e117d334f42e10a295e684c538c70432eb90758e21499c1a7
Tx public key: 70c7654f2a2f9a6f35fddd6dbfb9cb8af8c642f93513b927f4465c9a9b29613f
Timestamp: 1736838939 Timestamp [UCT]: 2025-01-14 07:15:39 Age [y:d:h:m:s]: 00:310:11:41:48
Block: 1197011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219418 RingCT/type: yes/0
Extra: 0170c7654f2a2f9a6f35fddd6dbfb9cb8af8c642f93513b927f4465c9a9b29613f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a7b689cb44568b527a9db960c6243f236e5d5ba834dbc50b24f076baa48204a 0.600000000000 1683616 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": 1197021, "vin": [ { "gen": { "height": 1197011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a7b689cb44568b527a9db960c6243f236e5d5ba834dbc50b24f076baa48204a" } } ], "extra": [ 1, 112, 199, 101, 79, 42, 47, 154, 111, 53, 253, 221, 109, 191, 185, 203, 138, 248, 198, 66, 249, 53, 19, 185, 39, 244, 70, 92, 154, 155, 41, 97, 63, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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