Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8826633ccb2b36da61d2a89ac78729abfce5f817b5c47f907b90b59015d55cea

Tx prefix hash: 2fd4ac00984089020bda9bf03e030efa0e157993efa988b39ef61ee4ac30ca30
Tx public key: 2b255990d3e6218e3da5c984c3cc323dae521fe744e510934b1574c42ade35a0
Timestamp: 1674797388 Timestamp [UCT]: 2023-01-27 05:29:48 Age [y:d:h:m:s]: 01:361:21:52:21
Block: 683682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519611 RingCT/type: yes/0
Extra: 012b255990d3e6218e3da5c984c3cc323dae521fe744e510934b1574c42ade35a0021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.331790314000 dcy

stealth address amount amount idx
00: 43c589f0b3f6b759dba2432d3e5c1f31fb7cc9c6e814af76a601659f552a346b 3.331790314000 1125877 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": 683692, "vin": [ { "gen": { "height": 683682 } } ], "vout": [ { "amount": 3331790314, "target": { "key": "43c589f0b3f6b759dba2432d3e5c1f31fb7cc9c6e814af76a601659f552a346b" } } ], "extra": [ 1, 43, 37, 89, 144, 211, 230, 33, 142, 61, 165, 201, 132, 195, 204, 50, 61, 174, 82, 31, 231, 68, 229, 16, 147, 75, 21, 116, 196, 42, 222, 53, 160, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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