Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aafbae61cc702933eb1d3fb4e75c1e12d23b3e4e7b9b81ff30479ea35ad5871

Tx prefix hash: cb88e70cf638925816a3cd56de25f75ec3cfbad1399131b990a9ea54623fdb92
Tx public key: 69db1ece74f93f5d1cad706526c0aefc05d4cb70057779b2665d72b5348036ef
Timestamp: 1636986841 Timestamp [UCT]: 2021-11-15 14:34:01 Age [y:d:h:m:s]: 04:039:05:24:18
Block: 374870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065210 RingCT/type: yes/0
Extra: 0169db1ece74f93f5d1cad706526c0aefc05d4cb70057779b2665d72b5348036ef0211000000054a0f5013000000000000000000

1 output(s) for total of 35.147987333000 dcy

stealth address amount amount idx
00: 9f36ff446f19300ce42a3b9fb588e9c0e9d15d58d7a094ef9aa7a06e59c791cf 35.147987333000 758676 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": 374880, "vin": [ { "gen": { "height": 374870 } } ], "vout": [ { "amount": 35147987333, "target": { "key": "9f36ff446f19300ce42a3b9fb588e9c0e9d15d58d7a094ef9aa7a06e59c791cf" } } ], "extra": [ 1, 105, 219, 30, 206, 116, 249, 63, 93, 28, 173, 112, 101, 38, 192, 174, 252, 5, 212, 203, 112, 5, 119, 121, 178, 102, 93, 114, 181, 52, 128, 54, 239, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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