Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3bdc77fbf7a75180202f5edb86d012e34510a2aee3af3c09f56efcd0feeb10

Tx prefix hash: c4360b8085f0d0344a5e535cdbcc86cfa70deffffca16c676838e5fba90ffbc7
Tx public key: 94a11d2b5a2bc826eb3726f58be73a88be992b210cc0263fecd4b07a4f32d47d
Timestamp: 1729359185 Timestamp [UCT]: 2024-10-19 17:33:05 Age [y:d:h:m:s]: 00:157:06:55:34
Block: 1135137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112176 RingCT/type: yes/0
Extra: 0194a11d2b5a2bc826eb3726f58be73a88be992b210cc0263fecd4b07a4f32d47d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98c26160571eb84ae509124a377aaabd6c1e9c6e19805c0ea2d059eb6c0182c0 0.600000000000 1618468 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": 1135147, "vin": [ { "gen": { "height": 1135137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98c26160571eb84ae509124a377aaabd6c1e9c6e19805c0ea2d059eb6c0182c0" } } ], "extra": [ 1, 148, 161, 29, 43, 90, 43, 200, 38, 235, 55, 38, 245, 139, 231, 58, 136, 190, 153, 43, 33, 12, 192, 38, 63, 236, 212, 176, 122, 79, 50, 212, 125, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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