Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cd66aa880dec26d5078c8aaa07c61537f03af106d673a1e29f9809e156faea4

Tx prefix hash: b6e31b15402ee34db1461d86b3bd57553427b06053abea3d96bbb2ebfc19933b
Tx public key: 8aeba4724191c5924a6bfc937a7ae145e07af045791eb8beb693b43106e83f18
Timestamp: 1700632289 Timestamp [UCT]: 2023-11-22 05:51:29 Age [y:d:h:m:s]: 01:184:18:32:33
Block: 896978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393278 RingCT/type: yes/0
Extra: 018aeba4724191c5924a6bfc937a7ae145e07af045791eb8beb693b43106e83f1802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.654545016000 dcy

stealth address amount amount idx
00: 3c1fbf41df5f351b5e685a79d5caadc579c48f1bac82e8e9c7b1d7efbc079e30 0.654545016000 1353329 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": 896988, "vin": [ { "gen": { "height": 896978 } } ], "vout": [ { "amount": 654545016, "target": { "key": "3c1fbf41df5f351b5e685a79d5caadc579c48f1bac82e8e9c7b1d7efbc079e30" } } ], "extra": [ 1, 138, 235, 164, 114, 65, 145, 197, 146, 74, 107, 252, 147, 122, 122, 225, 69, 224, 122, 240, 69, 121, 30, 184, 190, 182, 147, 180, 49, 6, 232, 63, 24, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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