Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288d31b3b80c95e145e2b0d77f40c79907bc443be49b8ce7d1faaf3dce6717fc

Tx prefix hash: bc9ae7c58d0721e3488f1e7ad7503148cb025193cca0a4556fe9f4d44d6fefa3
Tx public key: 9bfd2b6313a901531c840741837215ea34317564c0e4eb1ac3874ed443039341
Timestamp: 1714824595 Timestamp [UCT]: 2024-05-04 12:09:55 Age [y:d:h:m:s]: 01:002:14:07:18
Block: 1014659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262765 RingCT/type: yes/0
Extra: 019bfd2b6313a901531c840741837215ea34317564c0e4eb1ac3874ed4430393410211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7e9def69815df18f8b02dc48e70aaa31f1f0aa20d54be8471c2a23b4005dc2d 0.600000000000 1477808 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": 1014669, "vin": [ { "gen": { "height": 1014659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7e9def69815df18f8b02dc48e70aaa31f1f0aa20d54be8471c2a23b4005dc2d" } } ], "extra": [ 1, 155, 253, 43, 99, 19, 169, 1, 83, 28, 132, 7, 65, 131, 114, 21, 234, 52, 49, 117, 100, 192, 228, 235, 26, 195, 135, 78, 212, 67, 3, 147, 65, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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