Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a169fbf428f68f27b264175c0143c2cd0b1fbdee9bb79123ddd44d550530b6b0

Tx prefix hash: 27ffa9c89d807558cfde26f07e3bfabb70c657e1273d4ffdef295a3a6027e12f
Tx public key: 5ba1c90a53db11b32c1833e084a763b3c6936654ce97b336d7f7c239bfa27c14
Timestamp: 1755976197 Timestamp [UCT]: 2025-08-23 19:09:57 Age [y:d:h:m:s]: 00:086:02:18:12
Block: 1352893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61466 RingCT/type: yes/0
Extra: 015ba1c90a53db11b32c1833e084a763b3c6936654ce97b336d7f7c239bfa27c140211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34fb6e4fa4e06311a68ebb8bfeccd82289f93ee0344f9afcfd39f7a0126b435d 0.600000000000 1840862 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": 1352903, "vin": [ { "gen": { "height": 1352893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34fb6e4fa4e06311a68ebb8bfeccd82289f93ee0344f9afcfd39f7a0126b435d" } } ], "extra": [ 1, 91, 161, 201, 10, 83, 219, 17, 179, 44, 24, 51, 224, 132, 167, 99, 179, 198, 147, 102, 84, 206, 151, 179, 54, 215, 247, 194, 57, 191, 162, 124, 20, 2, 17, 0, 0, 0, 1, 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