Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641b733f8e356eac23b12af225173c803f5b1649500657c2d6fecf6247d83dfc

Tx prefix hash: ff6575a45f9c9dd29276f6c16dca0391e735e610bb91728def1a1f05e4f8b573
Tx public key: a439d75532d391e3e9053dfaaf3986e6d440a90368e797a2f88ddfa0b29c7ec6
Timestamp: 1730782164 Timestamp [UCT]: 2024-11-05 04:49:24 Age [y:d:h:m:s]: 00:019:02:53:09
Block: 1146852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13694 RingCT/type: yes/0
Extra: 01a439d75532d391e3e9053dfaaf3986e6d440a90368e797a2f88ddfa0b29c7ec6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b527d23770d3af3ef5a8e543999033f3fab179ed9ca58aeec42c137b0bf0c0c9 0.600000000000 1631543 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": 1146862, "vin": [ { "gen": { "height": 1146852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b527d23770d3af3ef5a8e543999033f3fab179ed9ca58aeec42c137b0bf0c0c9" } } ], "extra": [ 1, 164, 57, 215, 85, 50, 211, 145, 227, 233, 5, 61, 250, 175, 57, 134, 230, 212, 64, 169, 3, 104, 231, 151, 162, 248, 141, 223, 160, 178, 156, 126, 198, 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