Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7567f142ace702df65c71f54d79dd8c7ce6a3296492f22324a48f6218ab4bf5

Tx prefix hash: ba105a63eb2a2d4cc9998f5f44959ee13eae626117bd35f48bd633066bc9558e
Tx public key: b6c5708def8e28e399b7b50f7b569cd101100c7730588d1312b76e4ff8ec21e4
Timestamp: 1660555082 Timestamp [UCT]: 2022-08-15 09:18:02 Age [y:d:h:m:s]: 02:231:01:09:54
Block: 566285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686348 RingCT/type: yes/0
Extra: 01b6c5708def8e28e399b7b50f7b569cd101100c7730588d1312b76e4ff8ec21e4021100000005ec6d1a1a000000000000000000

1 output(s) for total of 8.159486483000 dcy

stealth address amount amount idx
00: c4d58c977f956cd91c02cbb8ab2e8f37a10242c84fcf9f8187759ea701e3ba9d 8.159486483000 999241 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": 566295, "vin": [ { "gen": { "height": 566285 } } ], "vout": [ { "amount": 8159486483, "target": { "key": "c4d58c977f956cd91c02cbb8ab2e8f37a10242c84fcf9f8187759ea701e3ba9d" } } ], "extra": [ 1, 182, 197, 112, 141, 239, 142, 40, 227, 153, 183, 181, 15, 123, 86, 156, 209, 1, 16, 12, 119, 48, 88, 141, 19, 18, 183, 110, 79, 248, 236, 33, 228, 2, 17, 0, 0, 0, 5, 236, 109, 26, 26, 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