Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e153feeb98178bb88f91ffbb28f4e846b883b08246ed71e7a9ccad2009065d1

Tx prefix hash: 598f511077380acb042ddaabddfb13d5343c9cb45c552e0ae526acc28ccccec5
Tx public key: 120b2a8479325853fb09e331f5b03c10e8a717c92a6a4ee47322f8b73dc1b21f
Timestamp: 1736595028 Timestamp [UCT]: 2025-01-11 11:30:28 Age [y:d:h:m:s]: 00:345:03:57:56
Block: 1194989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244248 RingCT/type: yes/0
Extra: 01120b2a8479325853fb09e331f5b03c10e8a717c92a6a4ee47322f8b73dc1b21f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ede142d6a393363a941539cf258fcb841954144683a5133aa7a4abe3b88d71ba 0.600000000000 1681570 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": 1194999, "vin": [ { "gen": { "height": 1194989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ede142d6a393363a941539cf258fcb841954144683a5133aa7a4abe3b88d71ba" } } ], "extra": [ 1, 18, 11, 42, 132, 121, 50, 88, 83, 251, 9, 227, 49, 245, 176, 60, 16, 232, 167, 23, 201, 42, 106, 78, 228, 115, 34, 248, 183, 61, 193, 178, 31, 2, 17, 0, 0, 0, 2, 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