Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32a9ddde200f60edf8645cef8550424e74dcecde1056bb05e306f08d608b67a1

Tx prefix hash: 880d5731d972777d8c7452769f526dce51001cc4b42d6aa5e99d3fea640e5580
Tx public key: 1a6aff3b99c9779531254f92f2a6796a442ed18aff8c4316c289711fb1e30bf5
Timestamp: 1696781423 Timestamp [UCT]: 2023-10-08 16:10:23 Age [y:d:h:m:s]: 01:220:12:29:46
Block: 865275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418654 RingCT/type: yes/0
Extra: 011a6aff3b99c9779531254f92f2a6796a442ed18aff8c4316c289711fb1e30bf502110000000141ee1c9b000000000000000000

1 output(s) for total of 0.833651943000 dcy

stealth address amount amount idx
00: b3ec7041d1f09a3a059479aa3d512271628adc93b0d10867700c2b7a06dd0172 0.833651943000 1319805 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": 865285, "vin": [ { "gen": { "height": 865275 } } ], "vout": [ { "amount": 833651943, "target": { "key": "b3ec7041d1f09a3a059479aa3d512271628adc93b0d10867700c2b7a06dd0172" } } ], "extra": [ 1, 26, 106, 255, 59, 153, 201, 119, 149, 49, 37, 79, 146, 242, 166, 121, 106, 68, 46, 209, 138, 255, 140, 67, 22, 194, 137, 113, 31, 177, 227, 11, 245, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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