Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbdca5c26162248f2119ce6648cf7794db652c0a387a4109de611be3252294a

Tx prefix hash: a1868c02663514ce8621f6b075b16892dfa831813c0943d5be0a8f0928eff6ce
Tx public key: 1e0fa928f3a4f99b4fb427c9e20a54640bfe0490121bb674b25e8af2db3d794a
Timestamp: 1737460675 Timestamp [UCT]: 2025-01-21 11:57:55 Age [y:d:h:m:s]: 00:148:05:23:10
Block: 1202120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105676 RingCT/type: yes/0
Extra: 011e0fa928f3a4f99b4fb427c9e20a54640bfe0490121bb674b25e8af2db3d794a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51788b3380b46739c763bd5b4553c985dd3aa674415c6713cf358d3cb6ea9c23 0.600000000000 1688779 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": 1202130, "vin": [ { "gen": { "height": 1202120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51788b3380b46739c763bd5b4553c985dd3aa674415c6713cf358d3cb6ea9c23" } } ], "extra": [ 1, 30, 15, 169, 40, 243, 164, 249, 155, 79, 180, 39, 201, 226, 10, 84, 100, 11, 254, 4, 144, 18, 27, 182, 116, 178, 94, 138, 242, 219, 61, 121, 74, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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