Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cc7bde8a6b3305c1a50b6fc8ff489beb66071d3d34f2df79e1a264c68a94f7

Tx prefix hash: 69c80b656d81e2a36072fdc8d2655a8ed76842796ea6f7a321bae1f291058419
Tx public key: e1ee9f7c5e3a0421e812f9497185477c779a8adae02c6fdc862bc1504a89545d
Timestamp: 1638774656 Timestamp [UCT]: 2021-12-06 07:10:56 Age [y:d:h:m:s]: 03:098:13:11:57
Block: 389500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849140 RingCT/type: yes/0
Extra: 01e1ee9f7c5e3a0421e812f9497185477c779a8adae02c6fdc862bc1504a89545d021100000015d6e4826b000000000000000000

1 output(s) for total of 31.435847818000 dcy

stealth address amount amount idx
00: caded2e3f288a536d10c63429157b29fce554f64d0d8fb0c90a1f33c552dfb36 31.435847818000 784683 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": 389510, "vin": [ { "gen": { "height": 389500 } } ], "vout": [ { "amount": 31435847818, "target": { "key": "caded2e3f288a536d10c63429157b29fce554f64d0d8fb0c90a1f33c552dfb36" } } ], "extra": [ 1, 225, 238, 159, 124, 94, 58, 4, 33, 232, 18, 249, 73, 113, 133, 71, 124, 119, 154, 138, 218, 224, 44, 111, 220, 134, 43, 193, 80, 74, 137, 84, 93, 2, 17, 0, 0, 0, 21, 214, 228, 130, 107, 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