Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3b1230507458d8f8fbaafaac8c095780979072cca522c53b1af855368c95ee

Tx prefix hash: 270a9f1d0a658d38f7ab561ccd22857cb47c6dca08b01316216e424e9a37a7c8
Tx public key: ae4360509c51fe6651ffc67fc5ec10caf05a2fb35834bd2ebc19e4267e40641a
Timestamp: 1697310286 Timestamp [UCT]: 2023-10-14 19:04:46 Age [y:d:h:m:s]: 01:171:18:04:15
Block: 869648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383776 RingCT/type: yes/0
Extra: 01ae4360509c51fe6651ffc67fc5ec10caf05a2fb35834bd2ebc19e4267e40641a021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.806297282000 dcy

stealth address amount amount idx
00: 0cc9db67f5a5a65f29163c433332adc8de7946fd5a8f02893202b58cc8a7f3d3 0.806297282000 1324497 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": 869658, "vin": [ { "gen": { "height": 869648 } } ], "vout": [ { "amount": 806297282, "target": { "key": "0cc9db67f5a5a65f29163c433332adc8de7946fd5a8f02893202b58cc8a7f3d3" } } ], "extra": [ 1, 174, 67, 96, 80, 156, 81, 254, 102, 81, 255, 198, 127, 197, 236, 16, 202, 240, 90, 47, 179, 88, 52, 189, 46, 188, 25, 228, 38, 126, 64, 100, 26, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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