Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3bfafac3203ca30e4d814e50ef159daafeafb2b970a38b7d9336f96ea3177ac

Tx prefix hash: 5c64f2ebc555d206ca5ccfb352055d7128d826a737dde3931ee5cbca52270fe9
Tx public key: ffbad87bb239f4ed2f88534f30fb1e8131495ae1cb74c264d3b5e5b42a73438b
Timestamp: 1741499686 Timestamp [UCT]: 2025-03-09 05:54:46 Age [y:d:h:m:s]: 00:257:11:00:56
Block: 1235340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181739 RingCT/type: yes/0
Extra: 01ffbad87bb239f4ed2f88534f30fb1e8131495ae1cb74c264d3b5e5b42a73438b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63dbc2fa9fdf0152e894628d6778552f3b7d7939f2c619d14012c5c60b416bac 0.600000000000 1722279 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": 1235350, "vin": [ { "gen": { "height": 1235340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63dbc2fa9fdf0152e894628d6778552f3b7d7939f2c619d14012c5c60b416bac" } } ], "extra": [ 1, 255, 186, 216, 123, 178, 57, 244, 237, 47, 136, 83, 79, 48, 251, 30, 129, 49, 73, 90, 225, 203, 116, 194, 100, 211, 181, 229, 180, 42, 115, 67, 139, 2, 17, 0, 0, 0, 5, 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