Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74be44b6be9575d8e8be7f2d5a76fbd6fb8e01bbeb3bd02934f384e441b75c9e

Tx prefix hash: ee00901b46fd86da71154b658117e3f8871f709dcc8ded6af1c47d14f505ff6e
Tx public key: 3f6a9f90f15cdad3cb3687a80a2329a5cad638119f9fa04a401de63edd2f5727
Timestamp: 1739486970 Timestamp [UCT]: 2025-02-13 22:49:30 Age [y:d:h:m:s]: 00:290:08:41:11
Block: 1218680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205290 RingCT/type: yes/0
Extra: 013f6a9f90f15cdad3cb3687a80a2329a5cad638119f9fa04a401de63edd2f5727021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb94e47a27b1edcf5b3128ec3a039b335c9b5e1bbba0180844587d2680d0a412 0.600000000000 1705499 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": 1218690, "vin": [ { "gen": { "height": 1218680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb94e47a27b1edcf5b3128ec3a039b335c9b5e1bbba0180844587d2680d0a412" } } ], "extra": [ 1, 63, 106, 159, 144, 241, 92, 218, 211, 203, 54, 135, 168, 10, 35, 41, 165, 202, 214, 56, 17, 159, 159, 160, 74, 64, 29, 230, 62, 221, 47, 87, 39, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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