Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c27fce6c1d727ba4a2bb3aed8c0e162fc117b43d6606ddb281c6ae4af6c24180

Tx prefix hash: 44cd3ab78bde923769db32bf7a673acd77a534d5d7dbee0bf523780e19da4fe0
Tx public key: 9cf4991615968f2e0f1401797ed0123556e5209e2aea610e05cfc81edf4d3cf2
Timestamp: 1751658221 Timestamp [UCT]: 2025-07-04 19:43:41 Age [y:d:h:m:s]: 00:139:08:18:01
Block: 1318802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97888 RingCT/type: yes/0
Extra: 019cf4991615968f2e0f1401797ed0123556e5209e2aea610e05cfc81edf4d3cf202110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5514afbb022f8394b115bd7af2ffa7b4927159c26ad26f83e8c64cad662f2a7a 0.600000000000 1806489 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": 1318812, "vin": [ { "gen": { "height": 1318802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5514afbb022f8394b115bd7af2ffa7b4927159c26ad26f83e8c64cad662f2a7a" } } ], "extra": [ 1, 156, 244, 153, 22, 21, 150, 143, 46, 15, 20, 1, 121, 126, 208, 18, 53, 86, 229, 32, 158, 42, 234, 97, 14, 5, 207, 200, 30, 223, 77, 60, 242, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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