Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3364b13adf6bc85f0fff9de7a356a0f8bdcbe9c17b297fe2c9bfa8d8cda52f34

Tx prefix hash: 79c3051ea46f4eb935bb286e29886002706abd4f7be9c5c0fa20905df542cdd7
Tx public key: c4b5e95d499c9316d9c897fae32f18d5e4df6b9c73df4daac1aa280d94e93838
Timestamp: 1757342337 Timestamp [UCT]: 2025-09-08 14:38:57 Age [y:d:h:m:s]: 00:142:02:08:06
Block: 1364121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101471 RingCT/type: yes/0
Extra: 01c4b5e95d499c9316d9c897fae32f18d5e4df6b9c73df4daac1aa280d94e9383802110000000aad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c0ef68c36ce4a4650458f6b5fcb9c5e5713517c597db98f87987326eeb940ea 0.600000000000 1852160 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": 1364131, "vin": [ { "gen": { "height": 1364121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c0ef68c36ce4a4650458f6b5fcb9c5e5713517c597db98f87987326eeb940ea" } } ], "extra": [ 1, 196, 181, 233, 93, 73, 156, 147, 22, 217, 200, 151, 250, 227, 47, 24, 213, 228, 223, 107, 156, 115, 223, 77, 170, 193, 170, 40, 13, 148, 233, 56, 56, 2, 17, 0, 0, 0, 10, 173, 121, 72, 208, 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