Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc5e267c09f955a226f35bcb0a893a7fe8112a340d97a51ecbff374b42af08d

Tx prefix hash: c9eb8b06581570f7af3490ec2aeac35ce0dec3d8692e4b157def962a472c7078
Tx public key: 91adedb9a683cb585acaa9773e3412b84b5fe527af824c308f5d0cdf8dfb3726
Timestamp: 1583026214 Timestamp [UCT]: 2020-03-01 01:30:14 Age [y:d:h:m:s]: 05:245:00:56:40
Block: 74408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1327220 RingCT/type: yes/0
Extra: 0191adedb9a683cb585acaa9773e3412b84b5fe527af824c308f5d0cdf8dfb37260211000000048a2ee0d9000000000000000000

1 output(s) for total of 347.901423633000 dcy

stealth address amount amount idx
00: 9e49518ed74ad0a2e4d21270e4df6ce27e6809ebde5091fbbdc670720d2fd1e0 347.901423633000 137706 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": 74418, "vin": [ { "gen": { "height": 74408 } } ], "vout": [ { "amount": 347901423633, "target": { "key": "9e49518ed74ad0a2e4d21270e4df6ce27e6809ebde5091fbbdc670720d2fd1e0" } } ], "extra": [ 1, 145, 173, 237, 185, 166, 131, 203, 88, 90, 202, 169, 119, 62, 52, 18, 184, 75, 95, 229, 39, 175, 130, 76, 48, 143, 93, 12, 223, 141, 251, 55, 38, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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