Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de6aef1d243b7aa9fc67aa677460c4f6e56860c6d93301cb35e9c0046f2fa021

Tx prefix hash: bcf5d7273bfa59f9c20dec250fe6c234540224a53427d7f562986dc4deadf3d6
Tx public key: c865d915232af4c3685983078925950c675fca75ffc0396a2ceb92b98fcbae46
Timestamp: 1636888591 Timestamp [UCT]: 2021-11-14 11:16:31 Age [y:d:h:m:s]: 03:013:15:10:56
Block: 374132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 788398 RingCT/type: yes/0
Extra: 01c865d915232af4c3685983078925950c675fca75ffc0396a2ceb92b98fcbae4602110000000df56b629f000000000000000000

1 output(s) for total of 35.346446781000 dcy

stealth address amount amount idx
00: 4e5686ffe0d4a9dfb25518c3a2d0c1964f8262e69c5c5596af7e410e7363bdd6 35.346446781000 757400 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": 374142, "vin": [ { "gen": { "height": 374132 } } ], "vout": [ { "amount": 35346446781, "target": { "key": "4e5686ffe0d4a9dfb25518c3a2d0c1964f8262e69c5c5596af7e410e7363bdd6" } } ], "extra": [ 1, 200, 101, 217, 21, 35, 42, 244, 195, 104, 89, 131, 7, 137, 37, 149, 12, 103, 95, 202, 117, 255, 192, 57, 106, 44, 235, 146, 185, 143, 203, 174, 70, 2, 17, 0, 0, 0, 13, 245, 107, 98, 159, 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