Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f65377d4c165c51c4083a74d5b004795240cc57dcac48da8fedcba2fc9b8824

Tx prefix hash: 4eff63811a85f40260fc55a4333d8b627a6df9e6c6db9922a54e3cc52260a03a
Tx public key: cce9e1f634da22e091d06dbc977ca0ce4128a030448c326a066795764cb6a0af
Timestamp: 1629688933 Timestamp [UCT]: 2021-08-23 03:22:13 Age [y:d:h:m:s]: 04:070:05:24:37
Block: 319064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1082754 RingCT/type: yes/0
Extra: 01cce9e1f634da22e091d06dbc977ca0ce4128a030448c326a066795764cb6a0af02110000000b01f1e57f000000000000000000

1 output(s) for total of 53.803308308000 dcy

stealth address amount amount idx
00: e81b3dd0c283952f2084dadb7b10bef9fdbafbe4a0303fdbdedf3409d2c9a565 53.803308308000 662995 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": 319074, "vin": [ { "gen": { "height": 319064 } } ], "vout": [ { "amount": 53803308308, "target": { "key": "e81b3dd0c283952f2084dadb7b10bef9fdbafbe4a0303fdbdedf3409d2c9a565" } } ], "extra": [ 1, 204, 233, 225, 246, 52, 218, 34, 224, 145, 208, 109, 188, 151, 124, 160, 206, 65, 40, 160, 48, 68, 140, 50, 106, 6, 103, 149, 118, 76, 182, 160, 175, 2, 17, 0, 0, 0, 11, 1, 241, 229, 127, 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