Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955dc0b6ecf2290b15eb168088f41908b0a2e75df4c8249fcdcaf3b0338e5134

Tx prefix hash: e4288ffaa4707a0cc0f819f7c76cf6d42cfa8455efcc79ae40b417f175c361ae
Tx public key: b2b09abc27b3b589790720cd507ea5773011a46170ee5aed71efb2a832b4ff4b
Timestamp: 1650083413 Timestamp [UCT]: 2022-04-16 04:30:13 Age [y:d:h:m:s]: 02:252:12:27:41
Block: 481157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700441 RingCT/type: yes/0
Extra: 01b2b09abc27b3b589790720cd507ea5773011a46170ee5aed71efb2a832b4ff4b0211000000044da16a3a000000000000000000

1 output(s) for total of 15.621666224000 dcy

stealth address amount amount idx
00: 45f17400364e07e269dec0d6f470f852b5af2cf8283898ed8e581cdb08d347fc 15.621666224000 902360 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": 481167, "vin": [ { "gen": { "height": 481157 } } ], "vout": [ { "amount": 15621666224, "target": { "key": "45f17400364e07e269dec0d6f470f852b5af2cf8283898ed8e581cdb08d347fc" } } ], "extra": [ 1, 178, 176, 154, 188, 39, 179, 181, 137, 121, 7, 32, 205, 80, 126, 165, 119, 48, 17, 164, 97, 112, 238, 90, 237, 113, 239, 178, 168, 50, 180, 255, 75, 2, 17, 0, 0, 0, 4, 77, 161, 106, 58, 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