Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52506c222ce7889533bd0c188ad18c6f028d3ba06ce2e941e6a5fe651290bc2e

Tx prefix hash: afc4fe1a6bb0618c7a3b2e403c36b07b212cd0a010a16ac8b790551cea2afae5
Tx public key: a54284b64c800f5d05844f818794a229cc814e3ddb9c288721abd3e027533241
Timestamp: 1617035471 Timestamp [UCT]: 2021-03-29 16:31:11 Age [y:d:h:m:s]: 03:340:04:25:20
Block: 229101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1002386 RingCT/type: yes/0
Extra: 01a54284b64c800f5d05844f818794a229cc814e3ddb9c288721abd3e027533241021100000006218d0d3b000000000000000000

1 output(s) for total of 106.879365171000 dcy

stealth address amount amount idx
00: 21eaf925f59a6e72ba6c06316acfe475e9b081f54ab85174732bf4eb6f6c7d66 106.879365171000 475323 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": 229111, "vin": [ { "gen": { "height": 229101 } } ], "vout": [ { "amount": 106879365171, "target": { "key": "21eaf925f59a6e72ba6c06316acfe475e9b081f54ab85174732bf4eb6f6c7d66" } } ], "extra": [ 1, 165, 66, 132, 182, 76, 128, 15, 93, 5, 132, 79, 129, 135, 148, 162, 41, 204, 129, 78, 61, 219, 156, 40, 135, 33, 171, 211, 224, 39, 83, 50, 65, 2, 17, 0, 0, 0, 6, 33, 141, 13, 59, 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