Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fbee5ffeda35a2213484b65349a49bc9423468ee2a788b8ce9c4586ab27af1d

Tx prefix hash: 26b77fafed15dc8d472f2196a3e896a0b9081e0d89d9eece9b0e12c5884219c4
Tx public key: 094afb933b10d4fb661ad6fbe7cba3d5220aedcbd450c7bbd4957872e6c284f2
Timestamp: 1713242505 Timestamp [UCT]: 2024-04-16 04:41:45 Age [y:d:h:m:s]: 00:315:02:33:16
Block: 1001517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225255 RingCT/type: yes/0
Extra: 01094afb933b10d4fb661ad6fbe7cba3d5220aedcbd450c7bbd4957872e6c284f202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02bc7c983df92dcbf425ea0bb8616cffd4ae5f7e5b9b26f969a1ea2af1e5e9f1 0.600000000000 1462023 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": 1001527, "vin": [ { "gen": { "height": 1001517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02bc7c983df92dcbf425ea0bb8616cffd4ae5f7e5b9b26f969a1ea2af1e5e9f1" } } ], "extra": [ 1, 9, 74, 251, 147, 59, 16, 212, 251, 102, 26, 214, 251, 231, 203, 163, 213, 34, 10, 237, 203, 212, 80, 199, 187, 212, 149, 120, 114, 230, 194, 132, 242, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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