Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1295f813e901d5d775a56103a2b7b0cf02f47eac3ec3a21a4dfe11b0aa45131f

Tx prefix hash: 2daa83d9c9e617e36f1cedce145de743e02074627b63c05386c667f1466853ab
Tx public key: 02257ac604ae227a131d1e361882f76a27d6e7430103ae3b16d8f78229ce22f2
Timestamp: 1635605629 Timestamp [UCT]: 2021-10-30 14:53:49 Age [y:d:h:m:s]: 02:333:06:33:56
Block: 363696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 755812 RingCT/type: yes/0
Extra: 0102257ac604ae227a131d1e361882f76a27d6e7430103ae3b16d8f78229ce22f2021100000007328bb496000000000000000000

1 output(s) for total of 38.278176573000 dcy

stealth address amount amount idx
00: d3541638e6752d4c85aa49fd889282bee0efbbd5829fcd0ebe161b66cb8bef97 38.278176573000 739106 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": 363706, "vin": [ { "gen": { "height": 363696 } } ], "vout": [ { "amount": 38278176573, "target": { "key": "d3541638e6752d4c85aa49fd889282bee0efbbd5829fcd0ebe161b66cb8bef97" } } ], "extra": [ 1, 2, 37, 122, 198, 4, 174, 34, 122, 19, 29, 30, 54, 24, 130, 247, 106, 39, 214, 231, 67, 1, 3, 174, 59, 22, 216, 247, 130, 41, 206, 34, 242, 2, 17, 0, 0, 0, 7, 50, 139, 180, 150, 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