Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271d2fd4f69f401d47b36c3ccf4e0e7b36c654a6e58c0f6b1184e1d478e300ea

Tx prefix hash: b1ec8b39478894888da9f677d12ecacb1df94bfd35c7082462d059a824217ff8
Tx public key: 2b719b1550721f9390b0b0d40d3051122e941be25879a2bee7c68e3c306f33ee
Timestamp: 1581824703 Timestamp [UCT]: 2020-02-16 03:45:03 Age [y:d:h:m:s]: 04:321:12:47:42
Block: 66068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121921 RingCT/type: yes/0
Extra: 012b719b1550721f9390b0b0d40d3051122e941be25879a2bee7c68e3c306f33ee021100000004724f989b000000000000000000

1 output(s) for total of 370.757631674000 dcy

stealth address amount amount idx
00: 7d4492f81a63744f4de63f9d0b2507f98f3addd66eef2f84a3c77f44b133dcd6 370.757631674000 121717 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": 66078, "vin": [ { "gen": { "height": 66068 } } ], "vout": [ { "amount": 370757631674, "target": { "key": "7d4492f81a63744f4de63f9d0b2507f98f3addd66eef2f84a3c77f44b133dcd6" } } ], "extra": [ 1, 43, 113, 155, 21, 80, 114, 31, 147, 144, 176, 176, 212, 13, 48, 81, 18, 46, 148, 27, 226, 88, 121, 162, 190, 231, 198, 142, 60, 48, 111, 51, 238, 2, 17, 0, 0, 0, 4, 114, 79, 152, 155, 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