Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ac5d03fd2e1408a27956cf2cde38f6519731f214454fe3e19d0f31d5145c6c8

Tx prefix hash: 226a052521aed7d5dcc6f3d5c066f1cdc7b9ef3f7b82c40e9a00aafc9e93b9ed
Tx public key: 73c7e5a55de2798e05b54cb05b567959384d36e95343c2212dfd089513c324c8
Timestamp: 1748700746 Timestamp [UCT]: 2025-05-31 14:12:26 Age [y:d:h:m:s]: 00:167:06:27:57
Block: 1294964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117229 RingCT/type: yes/0
Extra: 0173c7e5a55de2798e05b54cb05b567959384d36e95343c2212dfd089513c324c8021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4fc3eaf1520b0b9c28c56f0ac0bfd7e8acd3be0a27bad8c7dc012a99236868a 0.600000000000 1782461 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": 1294974, "vin": [ { "gen": { "height": 1294964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4fc3eaf1520b0b9c28c56f0ac0bfd7e8acd3be0a27bad8c7dc012a99236868a" } } ], "extra": [ 1, 115, 199, 229, 165, 93, 226, 121, 142, 5, 181, 76, 176, 91, 86, 121, 89, 56, 77, 54, 233, 83, 67, 194, 33, 45, 253, 8, 149, 19, 195, 36, 200, 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