Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a74d2d1bfb9190a661914ab5fa81d6c9cbcc40f25459fdd3fe799ba451e8f41

Tx prefix hash: f4ff008952683ac8babcebc877aa1647e1f188e792a665434249d659893b5b27
Tx public key: 6a5f6f4ebafbb1d11c0b53222f7cda830b7c5e0a6f16e2800f99165d8343483e
Timestamp: 1706714635 Timestamp [UCT]: 2024-01-31 15:23:55 Age [y:d:h:m:s]: 01:277:12:43:21
Block: 947392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457147 RingCT/type: yes/0
Extra: 016a5f6f4ebafbb1d11c0b53222f7cda830b7c5e0a6f16e2800f99165d8343483e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ae0f61d7ab6426977501b569226d79ca1748d692bc970777e0373b59cd7568c 0.600000000000 1405740 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": 947402, "vin": [ { "gen": { "height": 947392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ae0f61d7ab6426977501b569226d79ca1748d692bc970777e0373b59cd7568c" } } ], "extra": [ 1, 106, 95, 111, 78, 186, 251, 177, 209, 28, 11, 83, 34, 47, 124, 218, 131, 11, 124, 94, 10, 111, 22, 226, 128, 15, 153, 22, 93, 131, 67, 72, 62, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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