Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 478b62ae451c35789e103b9d7fe1ace10e18ba14895a1d54d42d309f35f5433b

Tx prefix hash: 6e33b3b8f64a6f1e0e6361005e20e8c436ffb2e36ab2d005353525c2de8d1dfa
Tx public key: 2fe4048b67f9817388c571e95514b5de83371daaa7a6b2b00238bc68fa66a8d6
Timestamp: 1736995389 Timestamp [UCT]: 2025-01-16 02:43:09 Age [y:d:h:m:s]: 00:152:17:30:24
Block: 1198304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108874 RingCT/type: yes/0
Extra: 012fe4048b67f9817388c571e95514b5de83371daaa7a6b2b00238bc68fa66a8d6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fbe51dfd459dab09098f1dc960301f425e689eb1711f7be95692c85a2d6970f 0.600000000000 1684927 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": 1198314, "vin": [ { "gen": { "height": 1198304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fbe51dfd459dab09098f1dc960301f425e689eb1711f7be95692c85a2d6970f" } } ], "extra": [ 1, 47, 228, 4, 139, 103, 249, 129, 115, 136, 197, 113, 233, 85, 20, 181, 222, 131, 55, 29, 170, 167, 166, 178, 176, 2, 56, 188, 104, 250, 102, 168, 214, 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