Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 079c4e46f52079f1ec378bf96b06234672f1f434a793f4fcee753da81e8aa2dd

Tx prefix hash: b438cb5bb8586028aac16c9fd8ec28dcc29734e5ea67e12dadf5bc2b6e4a6a52
Tx public key: b86aacde1c928a6869532c49a98ad7d4e805d44446940c05484d4179165ed09b
Timestamp: 1703981122 Timestamp [UCT]: 2023-12-31 00:05:22 Age [y:d:h:m:s]: 01:144:17:34:18
Block: 924745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364591 RingCT/type: yes/0
Extra: 01b86aacde1c928a6869532c49a98ad7d4e805d44446940c05484d4179165ed09b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e83b8f8a9dccbb0e7d4c1867869e99356dbd2fcd5f2d7ac60b5bea48bd7e7872 0.600000000000 1382501 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": 924755, "vin": [ { "gen": { "height": 924745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e83b8f8a9dccbb0e7d4c1867869e99356dbd2fcd5f2d7ac60b5bea48bd7e7872" } } ], "extra": [ 1, 184, 106, 172, 222, 28, 146, 138, 104, 105, 83, 44, 73, 169, 138, 215, 212, 232, 5, 212, 68, 70, 148, 12, 5, 72, 77, 65, 121, 22, 94, 208, 155, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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