Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 407ab6fb904bf532639654df33e37427d8616c407bc16183fc65224d9c44cab6

Tx prefix hash: 39ba72f79cef3f2848b0833c6e11636a108a4adf1cb1fefca275c99b3f8edd1b
Tx public key: e06a98978a3eecdfecbd76bade31e9e0e017530a7c5773462e06e33e20ddcbe5
Timestamp: 1734152636 Timestamp [UCT]: 2024-12-14 05:03:56 Age [y:d:h:m:s]: 00:095:18:19:13
Block: 1174792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68239 RingCT/type: yes/0
Extra: 01e06a98978a3eecdfecbd76bade31e9e0e017530a7c5773462e06e33e20ddcbe5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73dfc312ae209ff1d9c851b08d133a82968729628f2971273e9248d0687ef7e8 0.600000000000 1660989 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": 1174802, "vin": [ { "gen": { "height": 1174792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73dfc312ae209ff1d9c851b08d133a82968729628f2971273e9248d0687ef7e8" } } ], "extra": [ 1, 224, 106, 152, 151, 138, 62, 236, 223, 236, 189, 118, 186, 222, 49, 233, 224, 224, 23, 83, 10, 124, 87, 115, 70, 46, 6, 227, 62, 32, 221, 203, 229, 2, 17, 0, 0, 0, 4, 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