Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3be9ab303264e53ef54d384406b7ad07f7ea1c11a171d432a1e44e3fc58957

Tx prefix hash: f41c35632749c6791f5ae685d4d0918efcc17ba85d3591a4b49aa29c0d961420
Tx public key: 2399272547703509d57816f5f8fc3ff58c1c04fe4b1341a9d9416438c5ed55b2
Timestamp: 1736798708 Timestamp [UCT]: 2025-01-13 20:05:08 Age [y:d:h:m:s]: 00:158:02:14:47
Block: 1196677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112660 RingCT/type: yes/0
Extra: 012399272547703509d57816f5f8fc3ff58c1c04fe4b1341a9d9416438c5ed55b20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf7a3a134a410ebb8b0c8c8df2f3126442d1841d94c3bc52faf5e801e3aab2f 0.600000000000 1683278 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": 1196687, "vin": [ { "gen": { "height": 1196677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf7a3a134a410ebb8b0c8c8df2f3126442d1841d94c3bc52faf5e801e3aab2f" } } ], "extra": [ 1, 35, 153, 39, 37, 71, 112, 53, 9, 213, 120, 22, 245, 248, 252, 63, 245, 140, 28, 4, 254, 75, 19, 65, 169, 217, 65, 100, 56, 197, 237, 85, 178, 2, 17, 0, 0, 0, 2, 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