Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944ebd9562a5c6cc4c01eb84b3623c3e12f686e0be45edd5aa74d045b0618864

Tx prefix hash: dee775c9d888cfd42516c71c05a9d7a329a809292b2636fc000312e0dbd94eed
Tx public key: 896aaebd10289c84d53405a379e8049f71d2c00196296f2618a2cfdec6b52640
Timestamp: 1629293134 Timestamp [UCT]: 2021-08-18 13:25:34 Age [y:d:h:m:s]: 03:200:22:33:32
Block: 316451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 916923 RingCT/type: yes/0
Extra: 01896aaebd10289c84d53405a379e8049f71d2c00196296f2618a2cfdec6b5264002110000000a282c04e2000000000000000000

1 output(s) for total of 54.886677027000 dcy

stealth address amount amount idx
00: e39bb6f54c4684d3bda66f893c2f54176e085d20b77200d555e35e1c75cd3a5a 54.886677027000 658346 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": 316461, "vin": [ { "gen": { "height": 316451 } } ], "vout": [ { "amount": 54886677027, "target": { "key": "e39bb6f54c4684d3bda66f893c2f54176e085d20b77200d555e35e1c75cd3a5a" } } ], "extra": [ 1, 137, 106, 174, 189, 16, 40, 156, 132, 213, 52, 5, 163, 121, 232, 4, 159, 113, 210, 192, 1, 150, 41, 111, 38, 24, 162, 207, 222, 198, 181, 38, 64, 2, 17, 0, 0, 0, 10, 40, 44, 4, 226, 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