Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d4af502a12444fbc92688cd6ee7926d75bb68f934ce8280b73da87499d6bb5

Tx prefix hash: 854d0fcf0c3288f15f71b7b2c7d076181e1913d2f48e7dc1ee9e1bda2e384b12
Tx public key: f5618d77f3d18bf74ee86dfef83a5e892edc3a496b1f3db604e4945e526c89a8
Timestamp: 1582196181 Timestamp [UCT]: 2020-02-20 10:56:21 Age [y:d:h:m:s]: 05:080:18:33:59
Block: 68789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210877 RingCT/type: yes/0
Extra: 01f5618d77f3d18bf74ee86dfef83a5e892edc3a496b1f3db604e4945e526c89a8021100000003c71d3ff9000000000000000000

1 output(s) for total of 363.140170194000 dcy

stealth address amount amount idx
00: df4e2065d64d1873c099325b63f360112f32c1de9d9b87cc5838653f77a466f2 363.140170194000 126806 of 0

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": 68799, "vin": [ { "gen": { "height": 68789 } } ], "vout": [ { "amount": 363140170194, "target": { "key": "df4e2065d64d1873c099325b63f360112f32c1de9d9b87cc5838653f77a466f2" } } ], "extra": [ 1, 245, 97, 141, 119, 243, 209, 139, 247, 78, 232, 109, 254, 248, 58, 94, 137, 46, 220, 58, 73, 107, 31, 61, 182, 4, 228, 148, 94, 82, 108, 137, 168, 2, 17, 0, 0, 0, 3, 199, 29, 63, 249, 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