Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 489d39b9fa52ecfd1205e47a78966a0d52054d56ec5449c45f1e642edee0c2a8

Tx prefix hash: f998ddd4c8b719ee08142f8e4635cb14d000e0097ab042f895013760c0d0066d
Tx public key: 7ae2f299b4b0bc492f149c0a96dad2c95891ed6848d3d770eeb98310e579994f
Timestamp: 1738255122 Timestamp [UCT]: 2025-01-30 16:38:42 Age [y:d:h:m:s]: 00:295:07:24:20
Block: 1208478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208817 RingCT/type: yes/0
Extra: 017ae2f299b4b0bc492f149c0a96dad2c95891ed6848d3d770eeb98310e579994f02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28d6ef932c124175d3a9468a1ef2c568c0955f39c8a0a117dd2f06c8fc03aca 0.600000000000 1695211 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": 1208488, "vin": [ { "gen": { "height": 1208478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28d6ef932c124175d3a9468a1ef2c568c0955f39c8a0a117dd2f06c8fc03aca" } } ], "extra": [ 1, 122, 226, 242, 153, 180, 176, 188, 73, 47, 20, 156, 10, 150, 218, 210, 201, 88, 145, 237, 104, 72, 211, 215, 112, 238, 185, 131, 16, 229, 121, 153, 79, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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