Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2360238c0e0e5b05cabaf4bb76dbc624b6742fc54007ac50655da6d12fbe7864

Tx prefix hash: 2051442e07f445925108ccc5ab7c78cef72af88d2534de2fee6488ff41eabee0
Tx public key: fa13ff2c36df58c3ac9c16f56101784ad78c75c107d2d2ed9cca95dc4ddb04aa
Timestamp: 1760657427 Timestamp [UCT]: 2025-10-16 23:30:27 Age [y:d:h:m:s]: 00:041:21:35:33
Block: 1391518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29999 RingCT/type: yes/0
Extra: 01fa13ff2c36df58c3ac9c16f56101784ad78c75c107d2d2ed9cca95dc4ddb04aa0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f1e9eab32d4564d35a3fd2b72c73543da7d9d7ea4bd855caaea1128e47fd9c4 0.600000000000 1879765 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": 1391528, "vin": [ { "gen": { "height": 1391518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f1e9eab32d4564d35a3fd2b72c73543da7d9d7ea4bd855caaea1128e47fd9c4" } } ], "extra": [ 1, 250, 19, 255, 44, 54, 223, 88, 195, 172, 156, 22, 245, 97, 1, 120, 74, 215, 140, 117, 193, 7, 210, 210, 237, 156, 202, 149, 220, 77, 219, 4, 170, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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