Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bf62bddbd41a3fe1de68464b5745e4b6e1c5c63ba793631365841436c235dd6

Tx prefix hash: 7fe3f3f0b4cdb603bf4a010573d24653797677849a8bf6439823fc7fe201ee13
Tx public key: bd89197e94d85c1c0faeb50fc5ce077064fa17a585c6e38053bfdb4c41f3da75
Timestamp: 1681949340 Timestamp [UCT]: 2023-04-20 00:09:00 Age [y:d:h:m:s]: 01:353:19:03:50
Block: 742334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514126 RingCT/type: yes/0
Extra: 01bd89197e94d85c1c0faeb50fc5ce077064fa17a585c6e38053bfdb4c41f3da7502110000000275e3f0e9000000000000000000

1 output(s) for total of 2.129803394000 dcy

stealth address amount amount idx
00: 4471c2320b2a499cb0d10e8b6ba5730bbd48e962e9354c3890dd64d2d8cdd852 2.129803394000 1189295 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": 742344, "vin": [ { "gen": { "height": 742334 } } ], "vout": [ { "amount": 2129803394, "target": { "key": "4471c2320b2a499cb0d10e8b6ba5730bbd48e962e9354c3890dd64d2d8cdd852" } } ], "extra": [ 1, 189, 137, 25, 126, 148, 216, 92, 28, 15, 174, 181, 15, 197, 206, 7, 112, 100, 250, 23, 165, 133, 198, 227, 128, 83, 191, 219, 76, 65, 243, 218, 117, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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