Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a279a6082b52cf0b088187b4148864532ceead28fb02270351fbe6b72315b8

Tx prefix hash: aced09fb27afec3ba39297a3f77847b66b2d84a01ab0ad7877676ed313e428a8
Tx public key: 08ca6ae2ef323318cffeb9af0df527bb5f87c3029ff1bcddafebbf1a7b7357aa
Timestamp: 1733898409 Timestamp [UCT]: 2024-12-11 06:26:49 Age [y:d:h:m:s]: 00:112:21:13:33
Block: 1172690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80442 RingCT/type: yes/0
Extra: 0108ca6ae2ef323318cffeb9af0df527bb5f87c3029ff1bcddafebbf1a7b7357aa021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863f7de7bd00ffd12862a8bc8a5e69f5da5627d8f82a8d48d0a607f7dd44d9e2 0.600000000000 1658615 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": 1172700, "vin": [ { "gen": { "height": 1172690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863f7de7bd00ffd12862a8bc8a5e69f5da5627d8f82a8d48d0a607f7dd44d9e2" } } ], "extra": [ 1, 8, 202, 106, 226, 239, 50, 51, 24, 207, 254, 185, 175, 13, 245, 39, 187, 95, 135, 195, 2, 159, 241, 188, 221, 175, 235, 191, 26, 123, 115, 87, 170, 2, 17, 0, 0, 0, 4, 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