Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aba0c33eb1b7d8863085a57905d9dd79fb40cf51cf4a9f2370f20831dc3d93fe

Tx prefix hash: b671b56555cbcc71464f1c677a048b985041b70de100fca0b959a3ab99855834
Tx public key: 5eaac5cd7b9bd313194cace71be9cd510cf0a689cf6186599a19f1a12d327fb0
Timestamp: 1735961362 Timestamp [UCT]: 2025-01-04 03:29:22 Age [y:d:h:m:s]: 00:077:15:24:55
Block: 1189751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55273 RingCT/type: yes/0
Extra: 015eaac5cd7b9bd313194cace71be9cd510cf0a689cf6186599a19f1a12d327fb002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d38b8f8da2a917b712c86cac753929a924469c68e786e1f2169d1d96c18d44 0.600000000000 1676262 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": 1189761, "vin": [ { "gen": { "height": 1189751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d38b8f8da2a917b712c86cac753929a924469c68e786e1f2169d1d96c18d44" } } ], "extra": [ 1, 94, 170, 197, 205, 123, 155, 211, 19, 25, 76, 172, 231, 27, 233, 205, 81, 12, 240, 166, 137, 207, 97, 134, 89, 154, 25, 241, 161, 45, 50, 127, 176, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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