Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6955ca58d7b6293cd81072650696fb9853e0b8397cd99cf102719b659f393ac3

Tx prefix hash: 65362b3ea9e23ae8f17ee26398274b0149a655f52bba2c4639f520a7f7f58789
Tx public key: aaa6652ae3f75a9c4614fc35306f3ed5b8f99e066c337ad6a244387d13c58ab6
Timestamp: 1705139361 Timestamp [UCT]: 2024-01-13 09:49:21 Age [y:d:h:m:s]: 01:312:12:37:23
Block: 934335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482195 RingCT/type: yes/0
Extra: 01aaa6652ae3f75a9c4614fc35306f3ed5b8f99e066c337ad6a244387d13c58ab60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aabf79c021f9cc279529609248b8472f09c22e3a0e4bbcb9634769e2ba6e242c 0.600000000000 1392341 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": 934345, "vin": [ { "gen": { "height": 934335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aabf79c021f9cc279529609248b8472f09c22e3a0e4bbcb9634769e2ba6e242c" } } ], "extra": [ 1, 170, 166, 101, 42, 227, 247, 90, 156, 70, 20, 252, 53, 48, 111, 62, 213, 184, 249, 158, 6, 108, 51, 122, 214, 162, 68, 56, 125, 19, 197, 138, 182, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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