Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce38fb4d4ab85d67afbffda0a3e8148303a096e8589ff3d9d1a7d681cc60c56

Tx prefix hash: d06d51615078df95655cf0ef92990f82c3800abdae894259e83cfc03a4df8764
Tx public key: 713a9e6817cba6ae3f44a4356420800a177815056f793e6ea7d2ddf0d06dd36a
Timestamp: 1702505101 Timestamp [UCT]: 2023-12-13 22:05:01 Age [y:d:h:m:s]: 01:328:04:01:04
Block: 912511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493377 RingCT/type: yes/0
Extra: 01713a9e6817cba6ae3f44a4356420800a177815056f793e6ea7d2ddf0d06dd36a021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ed1cdcc689643a83b7f5bafb6fedb33a929bc5cc78c989e5636a311687ba06 0.600000000000 1369739 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": 912521, "vin": [ { "gen": { "height": 912511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ed1cdcc689643a83b7f5bafb6fedb33a929bc5cc78c989e5636a311687ba06" } } ], "extra": [ 1, 113, 58, 158, 104, 23, 203, 166, 174, 63, 68, 164, 53, 100, 32, 128, 10, 23, 120, 21, 5, 111, 121, 62, 110, 167, 210, 221, 240, 208, 109, 211, 106, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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