Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e2fff16d52a48f28e28a8ab1e1a2836f8344418236715af62dc6702633df4df

Tx prefix hash: 641ace5364557f5cf81d96d8b2cd58b22ab84f4a71f8c52ce336c93752de0c17
Tx public key: a9135199ff87af949e832303dda9de42c13c8d6e6340d385c9f1baf80b2248dd
Timestamp: 1731415987 Timestamp [UCT]: 2024-11-12 12:53:07 Age [y:d:h:m:s]: 00:142:23:15:55
Block: 1152107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102005 RingCT/type: yes/0
Extra: 01a9135199ff87af949e832303dda9de42c13c8d6e6340d385c9f1baf80b2248dd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5fd6a01e3f8d21b054e81c3c52a671acc64ae59e267122d24cb49a0aef9558 0.600000000000 1637698 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": 1152117, "vin": [ { "gen": { "height": 1152107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5fd6a01e3f8d21b054e81c3c52a671acc64ae59e267122d24cb49a0aef9558" } } ], "extra": [ 1, 169, 19, 81, 153, 255, 135, 175, 148, 158, 131, 35, 3, 221, 169, 222, 66, 193, 60, 141, 110, 99, 64, 211, 133, 201, 241, 186, 248, 11, 34, 72, 221, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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