Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa1a0e37da43495ff5f28b237c62b22bec71e142b64b10630ecb97c83f644a1

Tx prefix hash: afe9efc5c0e4e39924e4dabef3e694cd16dfd193f07c498519a81954b888944d
Tx public key: 0bea839ee3a18ef5a3283a1073e402c099befdb8da992157abd4bc6ae4afa1d6
Timestamp: 1721034047 Timestamp [UCT]: 2024-07-15 09:00:47 Age [y:d:h:m:s]: 01:116:15:08:16
Block: 1066141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341856 RingCT/type: yes/0
Extra: 010bea839ee3a18ef5a3283a1073e402c099befdb8da992157abd4bc6ae4afa1d602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0098bb67eae5f0b5ed3257e722f46976fe538856d17b79ae0c4f546d7aa09b69 0.600000000000 1536714 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": 1066151, "vin": [ { "gen": { "height": 1066141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0098bb67eae5f0b5ed3257e722f46976fe538856d17b79ae0c4f546d7aa09b69" } } ], "extra": [ 1, 11, 234, 131, 158, 227, 161, 142, 245, 163, 40, 58, 16, 115, 228, 2, 192, 153, 190, 253, 184, 218, 153, 33, 87, 171, 212, 188, 106, 228, 175, 161, 214, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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