Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d06e8baf5ddd5622af7b44fda6d5dcc8d6932de1dedcb2c2e1c379310ca63024

Tx prefix hash: 69815976191783cd948d7c6b68ce1b5930d927d91512fe9a5349c67fd85f1b6c
Tx public key: c214256ec3513d39ea648f1f71978034d04550a89af874ecc268d93270bbd9cf
Timestamp: 1705316865 Timestamp [UCT]: 2024-01-15 11:07:45 Age [y:d:h:m:s]: 01:044:20:55:17
Block: 935813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293136 RingCT/type: yes/0
Extra: 01c214256ec3513d39ea648f1f71978034d04550a89af874ecc268d93270bbd9cf0211000000220011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f43ef577e95e7ac245c087c4c9ed04a0210a431307e4cdb1b803dc79e682cf6 0.600000000000 1393831 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": 935823, "vin": [ { "gen": { "height": 935813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f43ef577e95e7ac245c087c4c9ed04a0210a431307e4cdb1b803dc79e682cf6" } } ], "extra": [ 1, 194, 20, 37, 110, 195, 81, 61, 57, 234, 100, 143, 31, 113, 151, 128, 52, 208, 69, 80, 168, 154, 248, 116, 236, 194, 104, 217, 50, 112, 187, 217, 207, 2, 17, 0, 0, 0, 34, 0, 17, 5, 91, 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