Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f3de9b9cfdff46425f702640871c0b74a7b40c0030aba38f3f7d4a2b6691ea

Tx prefix hash: 9fa2a3c303eb4bebf944c08ed5e9d818ca8b9b68043e6a87987cca880434f807
Tx public key: 42f7d29e8cb619716c7c94ddf2e13ff31206833701f0151dc652647d5354e8ff
Timestamp: 1734081273 Timestamp [UCT]: 2024-12-13 09:14:33 Age [y:d:h:m:s]: 00:109:11:00:44
Block: 1174211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77987 RingCT/type: yes/0
Extra: 0142f7d29e8cb619716c7c94ddf2e13ff31206833701f0151dc652647d5354e8ff021100000002e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a7eab80341e95e3ccba95eeb04e7c18c545f0bc9f7d5b58b62753de32ba3419 0.600000000000 1660336 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": 1174221, "vin": [ { "gen": { "height": 1174211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a7eab80341e95e3ccba95eeb04e7c18c545f0bc9f7d5b58b62753de32ba3419" } } ], "extra": [ 1, 66, 247, 210, 158, 140, 182, 25, 113, 108, 124, 148, 221, 242, 225, 63, 243, 18, 6, 131, 55, 1, 240, 21, 29, 198, 82, 100, 125, 83, 84, 232, 255, 2, 17, 0, 0, 0, 2, 232, 144, 243, 105, 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