Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d6a329500f15a945d56527c638e65e85ac6162bdda53d2dffe59c1082fc245

Tx prefix hash: f82cae1e57f5482f6fc8b05e366e1ec45832fe55a084c1526cbd589f98a727d7
Tx public key: 850075b0db7ce627b7ad8f2a2e60c697cd057162741c78c6dd56a944cc809a13
Timestamp: 1748999524 Timestamp [UCT]: 2025-06-04 01:12:04 Age [y:d:h:m:s]: 00:158:07:17:13
Block: 1297434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110807 RingCT/type: yes/0
Extra: 01850075b0db7ce627b7ad8f2a2e60c697cd057162741c78c6dd56a944cc809a13021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2735ab2959ec17640077e5c1fb71453f2bfd67b0709fd48adb623c2e8e10baa8 0.600000000000 1784953 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": 1297444, "vin": [ { "gen": { "height": 1297434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2735ab2959ec17640077e5c1fb71453f2bfd67b0709fd48adb623c2e8e10baa8" } } ], "extra": [ 1, 133, 0, 117, 176, 219, 124, 230, 39, 183, 173, 143, 42, 46, 96, 198, 151, 205, 5, 113, 98, 116, 28, 120, 198, 221, 86, 169, 68, 204, 128, 154, 19, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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