Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 811b2d27b8bcf9b6cedc7d3072e88dd6d63d2609c4f22a0b5c1728b9a976ea90

Tx prefix hash: 89b224ae3b925a0728fdcd3bc8506d32be01d1e2481541bd955fe520e1c80e8a
Tx public key: 9bc6fe9ec82ca41cacf8397b70af57176d1a2590152da7731081cff046b7c1f4
Timestamp: 1747577446 Timestamp [UCT]: 2025-05-18 14:10:46 Age [y:d:h:m:s]: 00:142:17:32:50
Block: 1285649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99653 RingCT/type: yes/0
Extra: 019bc6fe9ec82ca41cacf8397b70af57176d1a2590152da7731081cff046b7c1f402110000000b9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa5861b0fd243707c624880ac37dfe7c156c74635a3acc1fcac0cbc6cebc2c07 0.600000000000 1773114 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": 1285659, "vin": [ { "gen": { "height": 1285649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa5861b0fd243707c624880ac37dfe7c156c74635a3acc1fcac0cbc6cebc2c07" } } ], "extra": [ 1, 155, 198, 254, 158, 200, 44, 164, 28, 172, 248, 57, 123, 112, 175, 87, 23, 109, 26, 37, 144, 21, 45, 167, 115, 16, 129, 207, 240, 70, 183, 193, 244, 2, 17, 0, 0, 0, 11, 159, 159, 230, 140, 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