Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 572f249b0155921ce9ce86bdd97fc81d4d620f59ec10c21cc53744ee39c12d27

Tx prefix hash: 368f3442ad9e8f010c138aa21b4c7117f16f51a7b65173cb76b6eff89047319c
Tx public key: f41b39f71b7470ac0abfaecfd8974191c96191e9ecdfc7d029fc5f77a10d9e7d
Timestamp: 1732577487 Timestamp [UCT]: 2024-11-25 23:31:27 Age [y:d:h:m:s]: 00:348:22:33:48
Block: 1161731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246926 RingCT/type: yes/0
Extra: 01f41b39f71b7470ac0abfaecfd8974191c96191e9ecdfc7d029fc5f77a10d9e7d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b09f21ce15747d41f243e0715c67711e1b962f18517a74c4c6adfc2300de976b 0.600000000000 1647386 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": 1161741, "vin": [ { "gen": { "height": 1161731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b09f21ce15747d41f243e0715c67711e1b962f18517a74c4c6adfc2300de976b" } } ], "extra": [ 1, 244, 27, 57, 247, 27, 116, 112, 172, 10, 191, 174, 207, 216, 151, 65, 145, 201, 97, 145, 233, 236, 223, 199, 208, 41, 252, 95, 119, 161, 13, 158, 125, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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