Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc21143b0a377417fb1187b1b76826c984d9ef0ddd9a715f7e64263fa700a1bc

Tx prefix hash: e5d902bf17fd73c87385e5c32f734db4987fec75c44aa2f1470617e841958685
Tx public key: 763c983d84ad05b239b419f5656b28178426905d868491e08caabc6415f72b29
Timestamp: 1699861867 Timestamp [UCT]: 2023-11-13 07:51:07 Age [y:d:h:m:s]: 01:209:23:38:38
Block: 890600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411309 RingCT/type: yes/0
Extra: 01763c983d84ad05b239b419f5656b28178426905d868491e08caabc6415f72b2902110000000875e3f0e9000000000000000000

1 output(s) for total of 0.687183134000 dcy

stealth address amount amount idx
00: 65a1ebb79dfeb7c2b6b8d4b54c96077f2307fe061457e7bff4c41f2903db308f 0.687183134000 1346625 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": 890610, "vin": [ { "gen": { "height": 890600 } } ], "vout": [ { "amount": 687183134, "target": { "key": "65a1ebb79dfeb7c2b6b8d4b54c96077f2307fe061457e7bff4c41f2903db308f" } } ], "extra": [ 1, 118, 60, 152, 61, 132, 173, 5, 178, 57, 180, 25, 245, 101, 107, 40, 23, 132, 38, 144, 93, 134, 132, 145, 224, 140, 170, 188, 100, 21, 247, 43, 41, 2, 17, 0, 0, 0, 8, 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