Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233fd3204e956316fb4cc7da568ba682517875081cd9603fb73b8cb983ff3754

Tx prefix hash: a9ea1a17683a62ccfd4ca3126dac5dd38f1bd455ccccefa70ee0e768735cd68c
Tx public key: f3ba101e3fb19c245cde695c58db69e9aa302efe72a0406364b6927fa1957396
Timestamp: 1700454579 Timestamp [UCT]: 2023-11-20 04:29:39 Age [y:d:h:m:s]: 01:058:07:30:12
Block: 895517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303067 RingCT/type: yes/0
Extra: 01f3ba101e3fb19c245cde695c58db69e9aa302efe72a0406364b6927fa1957396021100000002faf35c9c000000000000000000

1 output(s) for total of 0.661881774000 dcy

stealth address amount amount idx
00: 739bd86d6b21d5c32333a45cf87bc007310c4aa81e8ffa7e46f6d862dff958e2 0.661881774000 1351754 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": 895527, "vin": [ { "gen": { "height": 895517 } } ], "vout": [ { "amount": 661881774, "target": { "key": "739bd86d6b21d5c32333a45cf87bc007310c4aa81e8ffa7e46f6d862dff958e2" } } ], "extra": [ 1, 243, 186, 16, 30, 63, 177, 156, 36, 92, 222, 105, 92, 88, 219, 105, 233, 170, 48, 46, 254, 114, 160, 64, 99, 100, 182, 146, 127, 161, 149, 115, 150, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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