Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c55c9efe9ba1e2959c7a7ecc4a4228369e4de06e34bef55727b7245ca3349f0a

Tx prefix hash: 274371b2064143e52350e1e6f28e6fdb88e68775203ea292ae138c90dbb0ff5f
Tx public key: bbf3fbf7a2a9459f2968854209461ec12ae535078285ad1e5d71a28cf58efcb3
Timestamp: 1644483860 Timestamp [UCT]: 2022-02-10 09:04:20 Age [y:d:h:m:s]: 03:264:07:16:03
Block: 435588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 966459 RingCT/type: yes/0
Extra: 01bbf3fbf7a2a9459f2968854209461ec12ae535078285ad1e5d71a28cf58efcb30211000000024da16a3a000000000000000000

1 output(s) for total of 22.116501782000 dcy

stealth address amount amount idx
00: 6a84b47688e6754d0a65422d5a0a6afdd226cb22f0d2816f60f27ce920079be5 22.116501782000 846811 of 0

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": 435598, "vin": [ { "gen": { "height": 435588 } } ], "vout": [ { "amount": 22116501782, "target": { "key": "6a84b47688e6754d0a65422d5a0a6afdd226cb22f0d2816f60f27ce920079be5" } } ], "extra": [ 1, 187, 243, 251, 247, 162, 169, 69, 159, 41, 104, 133, 66, 9, 70, 30, 193, 42, 229, 53, 7, 130, 133, 173, 30, 93, 113, 162, 140, 245, 142, 252, 179, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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