Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5faa7c7336a718b04a09a15c4960f441c2b5445a3c6256ac4911fb48f9925bda

Tx prefix hash: 27ad55c49b534c14d1e3791df72f6bc55ee076bfe840d8f35083726c5bc23d96
Tx public key: fd78a91c4c2e9248079f32f895c8ac45ef8ce15fa8c5479c0082cacf453e607b
Timestamp: 1724204280 Timestamp [UCT]: 2024-08-21 01:38:00 Age [y:d:h:m:s]: 00:095:06:41:10
Block: 1092416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68144 RingCT/type: yes/0
Extra: 01fd78a91c4c2e9248079f32f895c8ac45ef8ce15fa8c5479c0082cacf453e607b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ad4fb11c71b47c791d194efcddb9c525a39f31fd6e2e991637b72b0c5780e69 0.600000000000 1567157 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": 1092426, "vin": [ { "gen": { "height": 1092416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ad4fb11c71b47c791d194efcddb9c525a39f31fd6e2e991637b72b0c5780e69" } } ], "extra": [ 1, 253, 120, 169, 28, 76, 46, 146, 72, 7, 159, 50, 248, 149, 200, 172, 69, 239, 140, 225, 95, 168, 197, 71, 156, 0, 130, 202, 207, 69, 62, 96, 123, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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