Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24c1c94e5ceace199024aaf5c5a3499dfa2530436dd35fca9d213270a37dfc0

Tx prefix hash: 54336e922dcc2f2f3fb1fbbd64bd1977e55d4ea568fd7d26fd8af4945599ad5b
Tx public key: c6892a194fe4eff58c0f0a6069c820cbb0e65267d3b689e90d085d40abaf0edb
Timestamp: 1731193756 Timestamp [UCT]: 2024-11-09 23:09:16 Age [y:d:h:m:s]: 00:136:10:56:34
Block: 1150278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97324 RingCT/type: yes/0
Extra: 01c6892a194fe4eff58c0f0a6069c820cbb0e65267d3b689e90d085d40abaf0edb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 520ea578221c87b6c6438de7656fe8c3f216208edddb2ab32b37be9af97537e0 0.600000000000 1635539 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": 1150288, "vin": [ { "gen": { "height": 1150278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "520ea578221c87b6c6438de7656fe8c3f216208edddb2ab32b37be9af97537e0" } } ], "extra": [ 1, 198, 137, 42, 25, 79, 228, 239, 245, 140, 15, 10, 96, 105, 200, 32, 203, 176, 230, 82, 103, 211, 182, 137, 233, 13, 8, 93, 64, 171, 175, 14, 219, 2, 17, 0, 0, 0, 1, 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