Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 640ba2ec080091e14696690f26a9a37cb1417cbe7758472be6a1eb132b4a1227

Tx prefix hash: 0da1f49d71aef613cffe55a3ce8869da8625e189a227dd9fbc15fe215f1fe7f6
Tx public key: 371c6f09068cae1aae0ca162bce87277befe160e8ed4ccb5898d2b6b628d651a
Timestamp: 1577692982 Timestamp [UCT]: 2019-12-30 08:03:02 Age [y:d:h:m:s]: 05:034:12:00:58
Block: 34861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174434 RingCT/type: yes/0
Extra: 01371c6f09068cae1aae0ca162bce87277befe160e8ed4ccb5898d2b6b628d651a0211000000044ac5aa02000000000000000000

1 output(s) for total of 470.426621643000 dcy

stealth address amount amount idx
00: 8546408f2c4248baca7eae738ba2b1d0710b44815ea8f900629fe9801dbb7478 470.426621643000 58734 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": 34871, "vin": [ { "gen": { "height": 34861 } } ], "vout": [ { "amount": 470426621643, "target": { "key": "8546408f2c4248baca7eae738ba2b1d0710b44815ea8f900629fe9801dbb7478" } } ], "extra": [ 1, 55, 28, 111, 9, 6, 140, 174, 26, 174, 12, 161, 98, 188, 232, 114, 119, 190, 254, 22, 14, 142, 212, 204, 181, 137, 141, 43, 107, 98, 141, 101, 26, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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