Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c953774b47d41d9bdee706965e56389f694a6567370645eac6535f8943f78f

Tx prefix hash: a84d54331cd2447c0c74abf9ec1d8c5dbcc260e9031cbfc532fde4d3f37dc7ce
Tx public key: c32ea3bf412f7dd6aadf90c3499e61306923f1cdd14f10554378289e455714f1
Timestamp: 1723231861 Timestamp [UCT]: 2024-08-09 19:31:01 Age [y:d:h:m:s]: 00:250:08:34:34
Block: 1084348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178820 RingCT/type: yes/0
Extra: 01c32ea3bf412f7dd6aadf90c3499e61306923f1cdd14f10554378289e455714f1021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 108f832fcecd1a270a8eab14b078e5c4ebaf5fb4bf05d0028f29addd1e3f935d 0.600000000000 1558593 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": 1084358, "vin": [ { "gen": { "height": 1084348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108f832fcecd1a270a8eab14b078e5c4ebaf5fb4bf05d0028f29addd1e3f935d" } } ], "extra": [ 1, 195, 46, 163, 191, 65, 47, 125, 214, 170, 223, 144, 195, 73, 158, 97, 48, 105, 35, 241, 205, 209, 79, 16, 85, 67, 120, 40, 158, 69, 87, 20, 241, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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