Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 272f3facea6764a78b898b4d9189ddf66d545056c1b90ea244c7d5e71ac359e7

Tx prefix hash: 040d1cc1681f551406b69c60ea89a20a2a6d7d686f3bcb39e69fde8afd32728e
Tx public key: af4fbde8d83cebd2c2e4d75b443583b694ff418d5af9e821c977f28bb4ec2d5e
Timestamp: 1762163194 Timestamp [UCT]: 2025-11-03 09:46:34 Age [y:d:h:m:s]: 00:017:15:53:03
Block: 1403982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12636 RingCT/type: yes/0
Extra: 01af4fbde8d83cebd2c2e4d75b443583b694ff418d5af9e821c977f28bb4ec2d5e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d51a51266703fd364ac54c6b35290aa94c5d24ff3b239f408d4f7382fe7f362 0.600000000000 1892339 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": 1403992, "vin": [ { "gen": { "height": 1403982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d51a51266703fd364ac54c6b35290aa94c5d24ff3b239f408d4f7382fe7f362" } } ], "extra": [ 1, 175, 79, 189, 232, 216, 60, 235, 210, 194, 228, 215, 91, 68, 53, 131, 182, 148, 255, 65, 141, 90, 249, 232, 33, 201, 119, 242, 139, 180, 236, 45, 94, 2, 17, 0, 0, 0, 1, 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