Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9c15d6c505c44662e625dd3eeb1cc3618b42998ca8ebd115c303373de7f6a8

Tx prefix hash: 15bb8394fb25a15e09b696e58ea7ed579cc57a6e6f4b1a24f5930d477c848de2
Tx public key: 56e93cea0d17219e7def215bce924acae31d688a0b1ba4af3cbe733fc5d46a42
Timestamp: 1709176158 Timestamp [UCT]: 2024-02-29 03:09:18 Age [y:d:h:m:s]: 01:026:08:06:32
Block: 967826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279806 RingCT/type: yes/0
Extra: 0156e93cea0d17219e7def215bce924acae31d688a0b1ba4af3cbe733fc5d46a4202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45b8736f9d087267ac714eb3df6662a2a46d25daaca392828bebcec5f1aa8373 0.600000000000 1427617 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": 967836, "vin": [ { "gen": { "height": 967826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45b8736f9d087267ac714eb3df6662a2a46d25daaca392828bebcec5f1aa8373" } } ], "extra": [ 1, 86, 233, 60, 234, 13, 23, 33, 158, 125, 239, 33, 91, 206, 146, 74, 202, 227, 29, 104, 138, 11, 27, 164, 175, 60, 190, 115, 63, 197, 212, 106, 66, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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