Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f761464fd5c0d327c5dd1bb985610f869379476f2c02c7501e8278cc0bb9a498

Tx prefix hash: 0e23e85e166b8377770224dd967b5cf5b926ad2499c480ba0adc8616c99c29ab
Tx public key: e8fd1c3f246c8b25e335ead7db747bca3dfb17d42f58cb0c263f565a6213bc2d
Timestamp: 1729986170 Timestamp [UCT]: 2024-10-26 23:42:50 Age [y:d:h:m:s]: 00:233:20:21:15
Block: 1140324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166847 RingCT/type: yes/0
Extra: 01e8fd1c3f246c8b25e335ead7db747bca3dfb17d42f58cb0c263f565a6213bc2d021100000005a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9783c7e3f7d2e4d02947f46e7045cd5a0acbde8af4ecadf152b7b26e5c76993 0.600000000000 1624119 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": 1140334, "vin": [ { "gen": { "height": 1140324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9783c7e3f7d2e4d02947f46e7045cd5a0acbde8af4ecadf152b7b26e5c76993" } } ], "extra": [ 1, 232, 253, 28, 63, 36, 108, 139, 37, 227, 53, 234, 215, 219, 116, 123, 202, 61, 251, 23, 212, 47, 88, 203, 12, 38, 63, 86, 90, 98, 19, 188, 45, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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