Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299bbd0796719839f105fe51098fb5eb447c5fdec88c7fae097a3e44644a8086

Tx prefix hash: 6f4af9dc2d5b93d5de5955760efa7e316be1f12aa55c5d79f26196ce994cfb06
Tx public key: b827772113f4236f82b608fd7f821d3b1e0f21a5a863e4cecdeb8a4a6da52609
Timestamp: 1703186532 Timestamp [UCT]: 2023-12-21 19:22:12 Age [y:d:h:m:s]: 00:338:12:34:21
Block: 918157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242393 RingCT/type: yes/0
Extra: 01b827772113f4236f82b608fd7f821d3b1e0f21a5a863e4cecdeb8a4a6da526090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c10e544c760565217afc1762bfba57becf4c2d57f9b83e8c33347b06895c60 0.600000000000 1375799 of 15

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": 918167, "vin": [ { "gen": { "height": 918157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c10e544c760565217afc1762bfba57becf4c2d57f9b83e8c33347b06895c60" } } ], "extra": [ 1, 184, 39, 119, 33, 19, 244, 35, 111, 130, 182, 8, 253, 127, 130, 29, 59, 30, 15, 33, 165, 168, 99, 228, 206, 205, 235, 138, 74, 109, 165, 38, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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