Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09229ae204423d7652c28add838a7343bbf4c939fd3847119c42500dcdcecc2e

Tx prefix hash: b16d122feaa6b1d002375a5638bfba80940f41a065ee7771c242fbde7c6251b1
Tx public key: 592cbfdf1d51ca0ad576487ea4f3f3dac99d98e96596c4008c52dbe7a79569fa
Timestamp: 1745861508 Timestamp [UCT]: 2025-04-28 17:31:48 Age [y:d:h:m:s]: 00:206:01:26:32
Block: 1271446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144984 RingCT/type: yes/0
Extra: 01592cbfdf1d51ca0ad576487ea4f3f3dac99d98e96596c4008c52dbe7a79569fa0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 152892f5e5f5620b9fd16ba04a6d7fa9cca60df596a0d49f03a09763d582f691 0.600000000000 1758707 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": 1271456, "vin": [ { "gen": { "height": 1271446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "152892f5e5f5620b9fd16ba04a6d7fa9cca60df596a0d49f03a09763d582f691" } } ], "extra": [ 1, 89, 44, 191, 223, 29, 81, 202, 10, 213, 118, 72, 126, 164, 243, 243, 218, 201, 157, 152, 233, 101, 150, 196, 0, 140, 82, 219, 231, 167, 149, 105, 250, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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